revert: publish the full catalog rows in the release index - #4

My mistake, reverting #3.

#3 narrowed the index to five fields on the belief that the engine rejects the editorial ones. That belief came from a stale local threenative-engine checkout. On origin/develop the reader already declares them, on purpose:

// `kind`, `rating`, `genre` and `subgenre` are editorial catalog fields the data repository
// publishes and search never reads; a new catalog field is one name here and one schema change
// there, never a rejection of the whole release.

Proven, not assumed: the engine's own validateReferenceIndex from origin/develop accepts the v0.3 asset — ACCEPTED games=48 stubs=1363 rowKeys=9. The narrowing therefore drops fields the consumer publishes deliberately, so it goes.

Cut v0.5 after merge; no engine change is needed at all.